
<html><HEAD>
<LINK REL=STYLESHEET HREF="default.css" TYPE="text/css">
<TITLE>
Specifying target properties</TITLE>
</HEAD>
<BODY>

<!-- Header -->
<p class="ancestor" align="right"><A HREF="pbugp46.htm">Previous</A>&nbsp;&nbsp;<A HREF="pbugp48.htm" >Next</A>
<!-- End Header -->
<A NAME="CEGDIAIG"></A><h1>Specifying target properties</h1>
<A NAME="TI1446"></A><p>To set properties for a target, right-click the target in
the System Tree and select Properties from the pop-up menu. </p>
<p><img src="images/note.gif" width=17 height=17 border=0 align="bottom" alt="Note"> <span class=shaded>Close all painters</span> <A NAME="TI1447"></A>The tab pages in the target properties dialog box are disabled
if any painters are open.</p>
<A NAME="TI1448"></A><p>All target types have Library List and Deploy tabs. If there
is more than one project in the target, you can use the Deploy tab
page to specify which projects should be deployed and in which order. For
more information about setting deploy properties for workspaces
and targets, see <A HREF="pbugp12.htm#CEGJEBBB">"Building workspaces"</A>.</p>
<A NAME="TI1449"></A><p>Application server and EAServer component targets and .NET
targets have a Run tab, where you select the project to be used
for running and debugging the target. .NET targets also have a .NET
Assemblies tab that you use to import .NET assemblies into the target.</p>
<A NAME="CHDDJJFJ"></A><h2>Specifying the target's library search path</h2>
<A NAME="TI1450"></A><p>The objects you create in painters are stored in PowerBuilder
libraries (<ACRONYM title = "pibbles" >PBLs</ACRONYM>). You can use
objects from one library or multiple libraries in a target. You
define each library the target uses in the library search path.</p>
<A NAME="TI1451"></A><p>PowerBuilder uses the search path to find referenced objects
at runtime. When a new object is referenced, PowerBuilder looks
through the libraries in the order in which they are specified in
the library search path until it finds the object.</p>
<A NAME="TI1452"></A><p>On the Library List tab page of the Target Properties dialog
box, you can modify the libraries associated with the current target.</p>
<A NAME="TI1453"></A><p><img src="images/proc.gif" width=17 height=17 border=0 align="bottom" alt="Steps"> To specify the target's library search
path:</p>
<ol><li class=fi><p>In the Workspace tab of the System Tree,
right-click on the target containing your application and select
Library List from the pop-up menu.</p><p>The Target Properties dialog box displays the Library List
tab page. The libraries currently included in the library search
path are displayed in the list.</p></li>
<li class=ds><p>Do one of the following:<A NAME="TI1454"></A>
<ul>
<li class=fi>Enter
the name of each library you want to include in the Library Search
Path list, separating the names with semicolons.</li>
<li class=ds>Use the Browse button to include other libraries
in your search path.
</li>
</ul>

                      </p><p>You must specify libraries using an absolute path. To change
the order of libraries in the search path, use the pop-up menu to
copy, cut, and paste libraries.</p><p><img src="images/note.gif" width=17 height=17 border=0 align="bottom" alt="Note"> <span class=shaded>Make sure the order is correct</span> <A NAME="TI1455"></A>When you select multiple libraries from the Select Library
dialog box using Shift+click or Ctrl+click, the
first library you select appears last in the Library Search Path
list and will be the last library searched. </p>
<A NAME="TI1456"></A>To delete a library from the search path, select the library
in the list and use the pop-up menu or press Delete.</p>
</li>
<li class=ds><p>Click OK.</p><p>PowerBuilder updates the search path for the target.</p></li></ol>
<br><p><img src="images/note.gif" width=17 height=17 border=0 align="bottom" alt="Note"> <span class=shaded>Where PowerBuilder maintains the library search path</span> <A NAME="TI1457"></A>PowerBuilder stores your target's library search
path in the target (<i>.pbt</i>) file in a line beginning
with <FONT FACE="Courier New">LibList</FONT>; for example:<p><PRE> LibList "pbtutor.pbl;tutor_pb.pbl";</PRE></p>
<A NAME="CEGECBGE"></A><h2>Importing .NET assemblies</h2>
<A NAME="TI1458"></A><p>You can import .NET assemblies into .NET targets from the
.NET Assemblies page in the Properties dialog box for the target.
(Right-click on the target and select .NET Assemblies from the pop-up
menu.)</p>
<A NAME="TI1459"></A><p>Click the Browse button to open the Browse for a .NET Assembly
dialog box, from which you can browse to import private assemblies
with the .<i>dll</i>, .<i>tlb</i>, .<i>olb</i>, .<i>ocx</i>,
or .<i>exe</i> extension. To import an assembly, select
it and click Open. To import multiple assemblies, you must select
and import them one at a time.</p>
<A NAME="TI1460"></A><p>Click the Add button to open the Import .NET Assembly dialog
box, from which you can import a shared assembly into your target.
Assemblies must have a strong name. A strong name includes the assembly's
identity as well as a public key and a digital signature. For more
information about assemblies and strong names, see the <A HREF="http://msdn2.microsoft.com/en-us/library/wd40t7ad.aspx">Microsoft library</A>
.To import an assembly, select it
and click OK. To import multiple assemblies, you must select and
import them one at a time. </p>
<A NAME="TI1461"></A><p>You can also use the Import .NET Assembly dialog box to import
recently used assemblies. </p>
<A NAME="TI1462"></A><h4>System Tree display</h4>
<A NAME="TI1463"></A><p>The System Tree shows the classes, methods, structures, and
enumerations for C# assemblies that you import into your
.NET targets. However, a language-related limitation affecting
managed C++ assemblies prevents the System Tree
from displaying members of classes, structures, and enumeration types.
It also causes managed C++ classes to display
as structures.</p>
<A NAME="TI1464"></A><p>By default, the full name of each class in an assembly is
displayed in the System Tree. If you prefer to show only the final
name, add the following line to the [PB] section
of your <i>pb.ini</i> file:<p><PRE> SystemTree_DotNetFullName=0</PRE></p>
<A NAME="TI1465"></A><p>For example, with this setting the <b>Microsoft.SqlServer.Server.DataAccessKind</b> class
in <i>System.Data.dll</i> displays as <b>DataAccessKind</b>.
You can right-click the class and select Properties from the pop-up
menu to display the full class name.</p>

